Cropping examples

The Activities performed report provides a graphical display of the status of all activities during your simulation. A lot of information can be gained from displaying this report in the user interface or opened in a web browser in a separate window. We can learn the following about our simulation:

• Manage Maize and Manage vegetables are place holder activities with nothing specific to do each month but manage their child components so do not have a symbol displayed.
• We are able to see that the various crops are harvested in different months. The Manage crop product activities are performed every month as seen from the green or grey tick in every column. The columns with a green check mark indicate where a harvest took place. You can check that the harvest months correspond to your input data. Tomatoes are even harvested across multiple months.
• We can also see that the Sell Maize activity is performed every month, but only has something to do (sell maize) in the months where maize is harvested. If we look at the Sell tomato paste activity we see that the November sales Interval timer that only occurs in November each year is limiting when the Sell tomato paste activity is performed. Activities that are not performed because their timer was not active will display with a blank column.

The Labour requirements report provides a graphical display of where all labour was allocated in the simulation. Note, this is how labour is allocated and not the actual use of labour in the simulation.

• Two types of labour are provided in the simulation (named Male and Female) and six of the activities performed accept Labour requirements.
• The Sell Maize and Sell Tomato paste activities (Sell resource activity) are able to accept Labour requirement but none have been assigned in this simulation.
• Male labour is preferred for growing maize, but if insufficient, Female labour will be used. The opposite is true for growing tomatoes and making tomato paste.
• Only Female labour is possible for growing cucumbers.

The automated CLEM Resource ledger report for the Products store provides every transaction that occurred during the simulation. Click on this report component. In the Properties tab you will see that only our ProductStore is set for reporting. Next click the Data tab to see what transactions were produced.

• You can see all the entries providing gains (resource came into the store) coming from the harvest activities (Grow maize crop, Grow cucumbers and Grow tomatoes) as well as the Process tomato paste activity that produces a gain for Tomato paste and a loss for the Tomatoes store as expected.
• Losses from the store were also produced by the two sell activities
• Loss converted to value (price in Price_Loss column) is also included. No Price_gain column was added as there were no purchase pricing provided.

The automated CLEM Resource ledger report for the Finances store provides every transaction that occurred during the simulation. Click the Data tab to see what transactions were produced.

• The ledger starts with the initial bank balance of $100
• All gains to the bank account come from the various sales of maize and tomato paste.
• Losses (or expenses) come form the months where jars are purchased for making tomato paste.
• Loss converted to value (price in Price_Loss column) is also included. No Price_gain column was added as there were no purchase pricing provided.
• The category column uses the values provided in the simulation and allows us to group income and expenses into the various categories

The automated CLEM Resource ledger report for the Labour store provides every transaction that occurred during the simulation. Click the Data tab to see what transactions were produced.

• All transactions are losses as we can't gain labour (without buying hired labour that was not performed in this simulation.
• We can see labour transactions are categorised as Harvest or Process based on the categories supplied.
• The resource column could be used to report on labour used by type (e.g. Male and Female)
• The amount of labour used for each activity changes throughout the simulation as a result of being based on crop harvested and amount of tomato processed which are responding to the input data.

The automated CLEM Resource balances report provides balances at the end of each month for the Labour, ProductStore and Finances stores as dictated in the Properties tab. Click the Data tab to see the monthly balances.

• The labour (Male and Female columns) is the remaining days available at the end of the month. We can see that there is no shortfall of labour in our simulation requirements.
• Maize and Tomato balances are always zero as these are either sold or converted into tomato paste between the harvest and the end of the month.
• Tomato paste stores build up until sold in November each year
• The Cucumber store continues to increase. It is only now that we may realise we have a valuable resource that we have not sold during our simulation.
• The General_account column shows the bank balance. The overall increase suggests our maize and tomato paste farm is profitable. But, we also now realise we have not included any of the farm operating expenses.

The automated CLEM Resource shortfalls report provides presents every time a resource was in shortfall when requested.

• As expected from our ledger and balance reports the shortfall report is empty.
• This is a valuable report to check. The CLEM descriptive summary will also alert you when shortfalls occurred in your simulation.

The Activities performed report provides a graphical display of the status of all activities during your simulation. A lot of information can be gained from displaying this report in the user interface or opened in a web browser in a separate window. We can learn the following about our simulation:

• The rotation of crops is evident in the Manage wheat and Manage sorghum timing. The period in the middle of the simulation where Manage sorghum is performed also shows that three harvests were performed in this period (HarvestTag "first", "last" and one in between)
• The report shows that thee was insufficient labour available to fully perform both of the Transport wheat activities displayed with a pie symbol
• Some activities could not be performed due to the timing of crop rotation and harvests. These activities are displayed with an exclamation icon
• The various timers used in the simulation are all displayed at the bottom of the report that allow you to confirm the timing of all activities
• You can also note that the Sell sorghum activity has nothing to do on the first two occasions as there is no sorghum in the store until the first harvest occurs.

The automated CLEM Resource ledger report for the Products store provides every transaction that occurred during the simulation. Click on this report component. In the Properties tab you will see that only our ProductStore is set for reporting. Next click the Data tab to see what transactions were produced.

• The report shows all gains resulting from harvests performed by the Manage Wheat and Manage Sorghum activities
• The loss column is dominated by the monthly sale of Wheat from the store, and also includes a single Sell Sorghum transaction
• The value of all transactions is also provided.

The automated CLEM Resource ledger report for the Finances store provides every transaction that occurred during the simulation. Click the Data tab to see what transactions were produced.

• The ledger starts with the initial bank balance of $1000
• All gains to the bank account come from the various sales
• Losses (or expenses) come form the costs of harvesting wheat and sorghum
• Loss converted to value (price in Price_Loss column) is also included. No Price_gain column was added as there were no purchase pricing provided.

The automated CLEM Resource ledger report for the Labour store provides every transaction that occurred during the simulation. Click the Data tab to see what transactions were produced.

• All transactions are losses as we can't gain labour (without buying hired labour that was not performed in this simulation
• We can see labour transactions are categorised into a range of tasks for future analysis
• The resource column shows which individual "Male" of the 5 available was used for the task. Some tasks use the first individual, while others use the second individual, when the first individual has no availability
• Some tasks can be performed by a single individual (Male_1), while Transport wheat requires all five individuals to be performed

The automated CLEM Resource balances report provides balances at the end of each month for the Labour, ProductStore and Finances stores as dictated in the Properties tab. Click the Data tab to see the monthly balances.

• The labour (Male_1 to Male_5 columns) is the remaining days available at the end of the month. In most months these are 8, the value of availably monthly days we set in the Labour availability list in the Labour
• Wheat stored is 0 until the first harvest, after which is decreases by 5,000 kg sold each month
• Sorghum declines at each sale (July) with 10% of the store left as reserve
• The General_account column shows the bank balance. There is a decline from the opening balance to -2,120 in April 1905 after which the income from wheat sales increases the account

The automated CLEM Resource shortfalls report provides presents every time a resource was in shortfall when requested.

• As expected from our activity report and labour ledger the shortfall report is contains entries from the Transport wheat activity
• The entries show how much of the required resource was available indicating the severity of the shortfall. In our simulation 38 days of the required 47.16 days was provided